-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(meta): do configuration change in single barrier #20493
Conversation
❌ Rebase test pr failed: Error: Pull request #20493 is not created by gru-agent[bot] |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ee10be7
to
079b77c
Compare
2dbb354
to
2537f22
Compare
2537f22
to
ad38833
Compare
832be59
to
5bcc36c
Compare
ad38833
to
f7883df
Compare
f7883df
to
620c2e5
Compare
f421f54
to
856ea07
Compare
c4d9946
to
e2009bc
Compare
214fd61
to
7709bfc
Compare
7709bfc
to
c1a22bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I'm wondering if pause
and resume
will now be only for debugging purposes (through risectl
or pause_on_next_bootstrap
)? Do we have any further plan on them?
Not sure about that. For plan, do you mean remove them, or some enhancement on it? |
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Finalize and resolve #18312.
In this PR, we will
PausedReason
will be removed, and the pause and resume command will not hold aPausedReason
Checklist
Documentation
Release note